QRZ! Ham Radio 5/QRZ Ham Radio Callsign Database - Volume 5.iso/digests/tcp/940176.txt

Text File | 1994-11-13 | 18.0 KB | 724 lines

Date: Thu, 18 Aug 94 04:30:01 PDT
From: Advanced Amateur Radio Networking Group <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: TCP-Group Digest V94 #176
To: tcp-group-digest


TCP-Group Digest            Thu, 18 Aug 94       Volume 94 : Issue  176

Today's Topics:
                DAMA Implementaion and Interpretation
                      Okie Thoughts #2 (9 msgs)
                           Okie thoughts 2
                           PRUG WWW server
                         X1J gurus? (2 msgs)

Send Replies or notes for publication to: <[e-mail]>.
Subscription requests to <[e-mail]>.
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Thu, 18 Aug 94 08:51:01 EST
From: BARRY TITMARSH <[e-mail]>
Subject: DAMA Implementaion and Interpretation
To: TCP-GROUP <[e-mail]>, wnos-group <[e-mail]>

ARRL : 8th Computer Networking Conference - October 7, 1989 - page 203-209

            DAMA - A NEW METHOD OF HANDLING PACKETS ?
            ==========================================

by Detlef J. SCHMIDT, DK4EG   Steinbrecherstr. 22    D-38106 BRAUNSCHWEIG

                        NORD><LINK e.V.
                        c/o Peter Glzow, DB2OS
                        Allensteiner Str. 5
                        D-30880 LAATZEN
                        Germany

              Translation : Mark Bitterlich, WA3JPY
              Reprint     : Pierre Cornelis, ON7PC


ª...ß

Connect Establish :
-------------------

When a node attempts to connect to a user, the node adds the users ID to
it's polling list and begins to send SABMs to that station. If after a
certain amount of tries no UA is received, the user is assumed to be
inoperable and is removed from the polling list.

When a new user starts a connect sequence to the node, he begins by sending
SABMs to the master in a simple CSMA manner duplicating the existing method
used today. Collisions are possible during this phase, so it might be
necessary to repeat the SABMs several times until the node replies with a
UA. Once the node recognizes the users connection attempt, the users ID is
added to the polling list in a fashion very similar to the one used by
TheNet nodes (TheNet userlist) and the node (master) is now in control of
the uplink users station.

After the user sends SABMs and the node replies
with a UA,

the user replies with an RR0 to signal to the node that it had a
                         £££££££££££££
>>> this can also be interpreted as sending an I frame NR=0 NS=0
>>> if the upper layer has data to send in the case of tcpip
>>> Comments please ??

successful reception of UA.


ª...ß

uhf sent (Sun Aug 14 09:41:33 1994):
AX25: DC0HK to DB0RT-10 via DB0DAR SABM(P)

uhf recv (Sun Aug 14 09:41:41 1994):
AX25: DB0RT-10 to DC0HK via DB0DAR* UA(F) ªDAMAß

uhf sent (Sun Aug 14 09:41:41 1994):
AX25: DC0HK to DB0RT-10 via DB0DAR I NR=0 NS=0 pid=IP
IP: len 84 44.130.24.71->44.130.60.100 ihl 20 ttl 63 prot ICMP
ICMP: type Echo Request id 63232 seq 0
.............. !"#$%&'()*+,-./01234567


>>> as can be seen in the above trace.. I believe that at the time dama was
>>> invented it did not! consider upper layers of ax25 like tcpip and L3/L4
>>> netrom which acts the exact same way.


   Or have I read this the wrong way ?? I have a local dama digi sysop
who thinks different. Please some constructive comments, I have seen no
responce yet, from you guys.

Thanks Barry gm8sau/dc0hk

------------------------------

Date: Wed, 17 Aug 94 11:51:36
From: [e-mail]
Subject: Okie Thoughts #2
To: "Brian A. Lantz" <[e-mail]>, [e-mail]

> >  This message is in MIME format.  The first part should be readable text,
> >  while the remaining parts are likely unreadable without MIME-aware tools.

I, for one, was pleasantly surprised to see a MIME msg arrive here. This
means that altleast some of us are moving past the 1970's, 821 is all but
dead. Going forward is a good thing!

WAlt

------------------------------

Date: Wed, 17 Aug 94 12:53:30
From: [e-mail]
Subject: Okie Thoughts #2
To: [e-mail], "Brian A. Lantz" <[e-mail]>,

Walt said:
> I, for one, was pleasantly surprised to see a MIME msg arrive here.

Me too... wake up guys the future is already here with implementation of
RFC 1521...


Jack Spitznagel - KD4IZ

------------------------------

Date: Wed, 17 Aug 1994 14:58:16 -0400
From: "Brandon S. Allbery" <[e-mail]>
Subject: Okie Thoughts #2
To: [e-mail]

In your message of Wed, 17 Aug 1994 12:53:30, you write:
+---------------
| Me too... wake up guys the future is already here with implementation of
| RFC 1521...
+------------->8

The obvious question, however, is:  who's writing the MIME-capable external
mailer(s) for DOS (and especially, one for use with NOS)?  Let's face it; the
audience of tcp-group isn't all on Unix boxes.

++Brandon
--
Brandon S. Allbery KF8NH     [44.70.4.88]          [e-mail]
Linux development:  iBCS2, JNOS, MH

------------------------------

Date: Wed, 17 Aug 94 16:35:14
From: [e-mail]
Subject: Okie Thoughts #2
To: "Brandon S. Allbery" <[e-mail]>, [e-mail]

> The obvious question, however, is:  who's writing the MIME-capable
> external mailer(s) for DOS (and especially, one for use with NOS)?  Let's
> face it; the audience of tcp-group isn't all on Unix boxes.

Brandon, neither are we...Its OS/2 (as well as Unix). Not to start a jehad
(awgh but why not), I think the DOS folks are in for a rude awakening, I
dont know of anyone doing dosnos anymore, its OS/2 or Linux. And its tough
to fit anymore code into DOS anyways. The idea behind MIME is sending voice,
bmp's, exe's and data too. So, even if someone were willing to write the RFC
to DOS, what are you going to play the audio with and what are you going to
display the bmp's with...etc etc.
 Walt

------------------------------

Date: Wed, 17 Aug 1994 17:30:32 -0400
From: "Brandon S. Allbery" <[e-mail]>
Subject: Okie Thoughts #2
To: [e-mail]

In your message of Wed, 17 Aug 1994 16:35:14, you write:
+---------------
| Brandon, neither are we...Its OS/2 (as well as Unix). Not to start a jehad
| (awgh but why not), I think the DOS folks are in for a rude awakening, I
| dont know of anyone doing dosnos anymore, its OS/2 or Linux. And its tough
+------------->8

I know quite a few who are still on DOS, and I'm on record as disrecommending
JNOS for Linux for the average leaf node.  NOS for DOS still has some life in
it, especially when run under DESQview or MS-Windows (or OS/2, etc.) and
provided with decent external mailers.  I suspect that not even a stable
MS-Windows 4.x will kill off DOS any time soon; look how long Apple ][, CP/M,
etc. hung on against the IBM PC.

++Brandon
--
Brandon S. Allbery KF8NH     [44.70.4.88]          [e-mail]
Linux development:  iBCS2, JNOS, MH

------------------------------

Date: Wed, 17 Aug 1994 14:56:37 -0700
From: [e-mail] (Brian Kantor)
Subject: Okie Thoughts #2
To: [e-mail]

Until you have something that does MIME in a more natural way, feel free
to use the following little utility.
    - Brian



/*
 * Brian Kantor's stupid little MIME encode/decode utility
 *
 * I'm not proud of this code.
 *
 * this runs fine on a Sun.  Elsewhere, you're on your own.
 *
 * copyright (c) 1994 give it away but don't sell it
 */
#include <stdio.h>

int eflag = 0;
int hflag = 0;
int qflag = 0;

int lsz = 0;

main(argc,argv)
int argc;
char *argv[];
    {
    int c;

    if (argc < 2)
        {
        fprintf(stderr,"Usage: mime {-e|-d} [-h] {-b|-q}\n");
        exit(1);
        }

    while ( (c = getopt(argc, argv, "edhbq")) != -1)
        {
        switch(c)
            {
    case 'd':
            eflag = 0;
            break;
    case 'e':
            eflag = 1;
            break;
    case 'h':
            hflag = 1;
            break;
    case 'b':
            qflag = 0;
            break;
    case 'q':
            qflag = 1;
            break;
            }
        continue;
        }

    fprintf(stderr, "%s input, %scode %s\n",
        (hflag?"hex":"binary"),
        (eflag?"en":"de"), (qflag?"qp":"b64"));

    if (eflag)        /* encode */
        {
        if (qflag)
            qpencode();
        else
            b64encode();
        }
    else
        {        /* decode */
        if (qflag)
            qpdecode();
        else
            b64decode();
        }
    }

int
inchar()
    {
    char buf[4];

    if (hflag)
        {
        buf[0] = getchar();
        if (feof(stdin))
            return(EOF);
        buf[1] = getchar();
        if (feof(stdin))
            return(EOF);
        buf[3] = 0;
        return(strtol(buf, 0, 16));
        }
    else
        return(getchar());
    }


static char HEX[] = "0123456789ABCDEF";

int
qpencode()
    {
    int c, i;

    while (1)
        {
        c = inchar();
        if (c == EOF)
            return;

        /* EOL */
        if (c == 10)
            {
            putchar(c);
            lsz = 0;
            continue;
            }

        /* printable char not '=' */
        if (c >= 32 && c <= 126 && c != 61)
            {
            lchk(1,1);
            putchar(c);
            continue;
            }

        /* everything else gets encoded */
        lchk(3,1);
        putchar('=');
        putchar(HEX[(c & 0x0f0) >> 4]);
        putchar(HEX[(c & 0x0f)]);
        }
    }

lchk(n,q)
int n,q;
    {
    lsz += n;
    if (lsz > 72)
        {
        if (q)    /* qp encoded */
            puts("=");
        else
            putchar('\n');
        lsz = 0;
        }
    }


static char B64[] =
   "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";

int
b64encode()
    {
    int c, i;
    int bbuf[8];

    i = 0;
    bzero(bbuf, sizeof bbuf);

    while (1)
        {
        c = getc(stdin);
        if (feof(stdin))
            break;

        bbuf[i++] = c & 0xff;

        /* when we have 3 chars, squirt out 4 encoded bytes */
        if (i >= 3)
            {
            lchk(4,0);

            putchunk(3, bbuf);

            i = 0;
            bzero(bbuf, sizeof bbuf);
            }
        }

    putchunk(i, bbuf);
    }

putchunk(nc,bf)
int nc;
int bf[];
    {
    int np;

#define OB(x)  (putchar((B64[(x) & 63])))

    if (nc <= 0)
        return;
    if (nc > 3)
        return;

    if (nc > 0)
        {
        /* top six bits of first byte */
        OB((bf[0] & 0xfc) >> 2);
        /* bot 2 bits of first byte, top 4 bits of 2nd byte */
        OB(((bf[0] & 3) << 4) | ((bf[1] &0xf0) >> 4));
        }

    if (nc > 1)
        /* bot 4 bits of 2nd, top 2 bits of 3rd */
        OB(((bf[1] & 0x0f) << 2) | ((bf[2] & 0xc0) >> 6));

    if (nc > 2)
        /* bot 6 bits of 3rd */
        OB(bf[2]);

    np = 3 - nc;
    while (np-- > 0)
        putchar('=');
    }

/*
 * decode Quoted-Printable mime message line
 * squirts out as hex file image to ccmail file
 */
int
qpdecode()
    {
    int escaped;
    int c;
    char buf[4];

    escaped = 0;
    while (1)
        {
        c = inchar();
        if (c == EOF)
            return;

        if (c == '\n')
            {
            if (!escaped)    /* EOL == hard NL unless escaped */
                putchar(0x0a);
            escaped = 0;
            continue;
            }

        /* is it an unencoded character */
        if (c == '=')    /* QP escape character */
            {
            escaped = 1;
            continue;
            }

        /* not escaped, not escape char, output it */
        if (!escaped)
            {
            putchar(c & 0xff);
            continue;
            }

        /* expect two hex chars after escape */
        buf[0] = c;
        buf[1] = inchar();
        buf[3] = 0;
        c = strtol(buf, 0, 16);
        putchar(c);
        escaped = 0;
        continue;
        }
    }


/*
 * decodes base-64-encoded text
 * by turning each 4 base-64 characters into 3 8-bit bytes
 * and then outputting them
 */
b64decode()
    {
    char *b;
    int i;
    unsigned c, c1, c2, c3;
    int cc;

    i = 1;

    while((cc = inchar()) != EOF)
        {
        b = (char *)index(B64, cc);
        if (b == NULL)
            continue;

        c = (unsigned)(b - B64);

        switch(i++)
            {
    case 1:
            c1 = ( (c & 0x3f) << 2);    /* 1st 6 bits of c1 */
            c2 = c3 = 0;
            continue;
    case 2:
            c1 |= ( (c & 0x30) >> 4);    /* 2nd 2 bits of c1 */
            c2 = ( (c & 0x0f) << 4);    /* 1st 4 bits of c2 */
            continue;
    case 3:
            c2 |= ( (c & 0x3c) >> 2);    /* 2nd 4 bits of c2 */
            c3 = ( (c & 0x03) << 6);    /* 1st 2 bits of c3 */
            continue;
    case 4:
            c3 |= (c & 0x3f);        /* 2nd 6 bits of c3 */
            i = 1;
            break;
            }

        putchar(c1);
        putchar(c2);
        putchar(c3);
        }
    if (i == 4)
        fprintf(stderr, "early eof in b64decode\n");
    if (i == 2 || i == 3)
        putchar(c1);
    if (i == 3)
        putchar(c2);
    }

------------------------------

Date: Wed, 17 Aug 1994 15:31:49 -0700 (PDT)
From: Lyndon Nerenberg <[e-mail]>
Subject: Okie Thoughts #2
To: "Brandon S. Allbery" <[e-mail]>

In the PC world you can run Eudora under Windoze, or Pmail under raw DOS
as well as Windoze, if you require MIME support.

Both are freeware. (Yes, there is also a commercial version of Eudora,
but the free one works fine, too.)

--lyndon  VE7TCP/VE6BBM

------------------------------

Date: Thu, 18 Aug 1994 08:42:13 EET
From: "Markus Lamminmaki OH6LSA" <[e-mail]>
Subject: Okie Thoughts #2
To: [e-mail]

>+---------------
>| Me too... wake up guys the future is already here with implementation of
>| RFC 1521...
>+------------->8
>
>The obvious question, however, is:  who's writing the MIME-capable external
>mailer(s) for DOS (and especially, one for use with NOS)?  Let's face it; the
>audience of tcp-group isn't all on Unix boxes.
>
>++Brandon

Well, you could try PMAIL, you can get it working with NOS. Wery good
peace of software indeed, you can find it atleast in risc.ua.edu or
tyr.let.rug.nl.


---
Vasa Polytechnic              Email: [e-mail]
PB 6, SF-65201, FINLAND              [e-mail]
Fax: [phone]         Please, someone, make X.400 go away!
Work:[phone]         Home:  [phone]

        Death, drums and guitars, they finaly got it right! (B&Bh)

------------------------------

Date: Thu, 18 Aug 94 9:29:37 DST
From: Martin W Freiss <[e-mail]>
Subject: Okie Thoughts #2
To: [e-mail]

> > The obvious question, however, is:  who's writing the MIME-capable
> > external mailer(s) for DOS (and especially, one for use with NOS)?  Let's
> > face it; the audience of tcp-group isn't all on Unix boxes.
>
> Brandon, neither are we...Its OS/2 (as well as Unix). Not to start a jehad
> (awgh but why not), I think the DOS folks are in for a rude awakening, I
> dont know of anyone doing dosnos anymore, its OS/2 or Linux. And its tough
> to fit anymore code into DOS anyways. The idea behind MIME is sending voice,
> bmp's, exe's and data too. So, even if someone were willing to write the RFC
> to DOS, what are you going to play the audio with and what are you going to
> display the bmp's with...etc etc.

With external programs spawned by the mailer. I do it this way with PCElm 3.21,
which does it crudely, but it works, using freeware and shareware programs
to play voicemail through a soundblaster card and view JPG pictures.
This approach is suggested in one of the RFCs (I forgot the number)  about
MIME, and is both easy to code and easy to configure.

So, MIME works under DOS. Of course, an integrated multimedia work
environment with mail under DOS (something like Andrew) will be nigh impossible.

Trying to send digitized voice over a congested 1200 Bd packet link is another
matter entirely :-)

-Martin

--
 Martin Freiss               | R&D computer center | [e-mail]
 Siemens Nixdorf Infosystems | Dept. MR OI 4       | NIC MF194
 Paderborn, Germany          | Phone [phone]
"The average pointer, statistically, points somewhere in X." -Hugh Redelmeier

------------------------------

Date: Thu, 18 Aug 94 09:03:00 BST
From: Martin Lines <[e-mail]>
Subject: Okie thoughts 2
To: [e-mail]

Haven't we gone around the same loop again?

Shouldn't NOS be acting as a front-end comms box. Mine
is and as a consequence who cares that it runs on DOS?.

Surely its up to the mailer how it handles MIME etc not the mail
infrastructure and there are a few suitable MIME mailers
around for use on any access system (Windows etc)

Flames to /dev/null

Martin Lines

[e-mail]

------------------------------

Date: Thu, 18 Aug 1994 20:10:44 +0900
From: Isao SEKI <[e-mail]>
Subject: PRUG WWW server
To: [e-mail]

Hi ALL,

We have exported WWW server at "Hamfair '94" on japanese day time
(UT -0900) from today to Aug.21. At server had many japanese euc
text and many PRUG members pictures.
    http://pdemo01.hamfair.prug.or.jp/
    (163.213.30.1)
And we have exported every time
    http://www.prug.or.jp/

PRUG - Packet Radio Users' Group
Hamfair - Bigest ham's festival at Japan.

Isao
---
Isao SEKI / JM1WBB (HAM Radio)
EMail: [e-mail] (NeXT Mail OK) / [e-mail]

------------------------------

Date: Wed, 17 Aug 94 08:17:20 CDT
From: [e-mail] (Michael H. Foster)
Subject: X1J gurus?
To: [e-mail], [e-mail]

Has anyone optimized their x1j parms?
With several band openings over the past few weeks, the x1j's locally
lose their buffer space and hose up until a reset is given.  We are
trying different parm settings hoping the node will release it's buffer
space faster, but we have no serious documentation to guide these settings.
Can anyone provide any insight or specifics?

Thanks in advance,
Mike, wa5txx
[e-mail]

------------------------------

Date: Thu, 18 Aug 1994 02:38:49 -0700 (PDT)
From: Bob Merritt <[e-mail]>
Subject: X1J gurus?
To: "Michael H. Foster" <[e-mail]>

On Wed, 17 Aug 1994, Michael H. Foster wrote:

> Has anyone optimized their x1j parms? > With several band openings over
the past few weeks, the x1j's locally > lose their buffer space and hose
up until a reset is given.  We are > trying different parm settings hoping
the node will release it's buffer > space faster, but we have no serious
documentation to guide these settings. > Can anyone provide any insight or
specifics?  >

Mike...  we found that decreasing the max # of nodes to 30,
and increasing the min qual to abt 120 helps the most in that area.  Other
things to do is to disable help, and reduce the mheard #.  Also, we
installed a 10MHz speed up kit from Paccomm that keeps the buffers up near
600-700 and cpu looping at 900-1200.  Hope that helps...

73/bob

*******
Bob Merritt  KA4BYP  ----->  [e-mail]  <-----

------------------------------

End of TCP-Group Digest V94 #176
******************************